home *** CD-ROM | disk | FTP | other *** search
/ ftp.cs.arizona.edu / ftp.cs.arizona.edu.tar / ftp.cs.arizona.edu / icon / newsgrp / group97a.txt / 000137_icon-group-sender _Sat Jun 14 18:51:24 1997.msg < prev    next >
Internet Message Format  |  2000-09-20  |  1KB
  1. Received: from kingfisher.CS.Arizona.EDU by cheltenham.cs.arizona.edu; Mon, 16 Jun 1997 08:43:33 MST
  2. Received: by kingfisher.CS.Arizona.EDU; (5.65v3.2/1.1.8.2/08Nov94-0446PM)
  3.     id AA10788; Mon, 16 Jun 1997 08:43:32 -0700
  4. To: icon-group@cs.arizona.edu
  5. Date: 14 Jun 1997 18:51:24 GMT
  6. From: guy@orion.math.tau.ac.il (Guy Laden)
  7. Message-Id: <5nup7c$6lp$1@beet.tau.ac.il>
  8. Organization: School of Mathematical Sciences, Tel Aviv University, Israel.
  9. Sender: icon-group-request@cs.arizona.edu
  10. Subject: Writing daemons in Icon - signal handling
  11. Errors-To: icon-group-errors@cs.arizona.edu
  12. Status: RO
  13. Content-Length: 436
  14.  
  15. Can anybody offer any advice or examples of _robust_ daemons which
  16. listen to network sockets, written in Icon.
  17. How should signals be handled?
  18. Whats the 'right' way of handling timeouts of network connections?
  19. Does one just write wrappers for the corresponding C functions?
  20. I need to implement a small but reliable client-server system and 
  21. am hoping others can verify its been done before and that Icon is 
  22. up to the job.
  23.  
  24. Thanks,
  25. Guy
  26.